<script>‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû Script info for this cd btn id 28. ‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû
put "E-Mail:" & myTab & theEMail & return after probDesc
put "Mail Type:" & myTab & theEMailType & return after probDesc
end if
if reply is true then
put "Reply Requested:" & myTab & "Yes" & return after probDesc
else
put "Reply Requested:" & myTab & "No" & return after probDesc
end if
put addPadding(probDesc) into probDesc
put the number of chars of probDesc into numChars
put "Description:" & myTab & numChars & return after theMessage
put probDesc & return after theMessage
-- WRITE: end of file marker
put return after theMessage
put "End of File " & textFileVersion() & return after theMessage
-- SEND BACK ALL THIS INFORMATION SO IT CAN REALLY BE WRITTEN
return theMessage
end exportText
-- getNumber, used in exportText above
function getNumber whichField,whichList
put FALSE into found
repeat with nn=1 to the number of lines of whichList
if whichField = line nn of whichList then
put TRUE into found
exit repeat
end if
end repeat
if found is TRUE then
return nn
else
return -1
end if
end getNumber
</script>
</part>
<part>
<id>32</id>
<type>button</type>
<visible> <false /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>320</left>
<top>318</top>
<right>429</right>
<bottom>338</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Cover</name>
<script>on mouseUp
-- do nothing
end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>35</id>
<text>When running A/UX 3.1 in 32-bit mode, BasketWeaver Pro 1.6 crashes on launch.
BasketWeaver does not crash in 24-bit mode, nor does it crash in Mac OS in either 32- or 24-bit modes.
To reproduce the bug:
1) Launch A/UX 3.1
2) Log in as root in 32-bit mode
3) Doubleclick on BasketWeaver Pro 1.6
==> Boom! Application crashes with bus error at CRASHHERE + 0004</text>
</content>
<content>
<layer>background</layer>
<id>54</id>
<text>CPU: Macintosh Quadra 950, 12MB RAM
KEYBOARD: Apple Adjustable Keyboard
MONITORS: Macintosh 21-inch Color Display
Miscellaneous: No Extensions are running.
Also happens on a Mac II, a IIfx and a Quadra 700.
This problem has been around since A/UX 3.0 and BasketWeaver 1.0.</text>
</content>
<content>
<layer>card</layer>
<id>27</id>
<text><span class="style3">bout the Example Problem Report
</span><span class="style2">
This is a sample problem report, written in the style that we like to see problems written. The Summary field is concise, the Problem Description field has the steps needed to repeat the bug, the Configuration field has enough information about the Macintosh you did your testing on so that we can recreate the environment in which you found the problem.
None of the fields are modifiable because the bug has already been sent. For the same reason, when you choose any of the popup menus, nothing changes.
Buttons with down arrows after them are popup menus.
You can click "Done" before sending a problem report if you aren't ready to send (perhaps you need to go find out more information about the problem).
You can delete this example problem after you have created at least one problem report of your own.</span></text>
</content>
<content>
<layer>background</layer>
<id>62</id>
<text>(Example Bug) BasketWeaver Pro crashes on launch when running under A/UX 3.1.</text>
</content>
<content>
<layer>background</layer>
<id>45</id>
<text>Always</text>
</content>
<content>
<layer>background</layer>
<id>50</id>
<text>Causes Crash</text>
</content>
<content>
<layer>background</layer>
<id>60</id>
<text>Will Affect User</text>
</content>
<content>
<layer>background</layer>
<id>43</id>
<text>AUX</text>
</content>
<content>
<layer>background</layer>
<id>66</id>
<text>1212.000</text>
</content>
<content>
<layer>background</layer>
<id>69</id>
<text>This report has been sent.
You cannot modify it.
</text>
</content>
<name>Sample Problem Description</name>
<script>‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû Script info for this card. ‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû‚àû
<text>This card lists all of the bugs you have reported. From here you can go to any Problem Report, just by clicking on its title.</text>
</content>
<content>
<layer>card</layer>
<id>15</id>
<text>0</text>
</content>
<content>
<layer>card</layer>
<id>18</id>
<text>
Apple, the Apple logo, AppleLink, A/UX, AppleTalk, HyperCard and Macintosh are trademarks of Apple Computer, Inc. registered in the USA and other countries. PowerBook Duo, Macintosh Quadra, Macintosh Performa, Macintosh Centris and Macintosh Classic are trademarks of Apple Computer, Inc.
CompuServe is a registered service mark of CompuServe, Inc.
UNIX is a special trademark of UNIX System Laboratories, Inc.
NFS is a trademark of Sun Microsystems, Inc.
Internet is a trademark of Digital Equipment Corporation.</text>
</content>
<content>
<layer>background</layer>
<id>23</id>
<text>N o t e s f o r A n y o n e M o d i f y i n g T h i s S t a c k
Most of the popup-menus and many other parts of this stack can be modified without scripting. Here are a few of the back-doors as I remember them:
• To change the AppleLink that bugs are sent to: modify the 'STR ' resource called "APPLELINK".
• All (or almost all) text strings can be found in 'STR ' resources. (This makes the stack more easily localizeable, and gets all the text out of my stack script).
H e l p T e x t
• To change the Help Text, in the message box type 'show bg fld "Help Text" ' on the cover card. It is a background field, so go to the background (command-B) to edit it.
P o p u p M e n u s
• To modify the text of a popup (such as the list of components), while looking at a card with the popup, type "alllist" in the message box. The fields containing the text for the popups will all become visible. They are editable if you are in the background.
F o n t s
• The "Apple Bug Reporter" text at the top of the cards is in Apple Garamond Bk 34pt Condensed.
• All text fields are Geneva 9pt (some text is bold or italic).
• All buttons are in Chicago 12pt.
U s e f u l 'S T R ' R e s o u r c e s
• AppleLink -- the address to which bugs are sent
• AppleLink CC -- an additional address to add as the default (user can change it in Send dialog)
• ComponentText -- the default component to fill in on New problem reports (usually blank)
• Keywords -- additional keywords to add to a bug report ("External" is automatically added). Make sure the Keywords are already in Radar before adding to this list. Separate keywords with commas.
• Default Mail Type" - Usually this is "AppleLink", but we may change this to "e-World" eventually; also used in conjunction with server variables below when saving to a file server.
• "Server Zone Name","Server Name","Server Volume Name","Server Folder Name","Server Default User Name" -- these strings are used to specify a server to save bug reports to. See "Using a File Server" below
U s i n g A F i l e S e r v e r
There are several 'STR ' resources you should set if you are planning on saving bugs to a file server rather than sending them to AppleLink. This feature would be useful if you had a lab with many machines and wanted to collect the bugs into groups before sending them.
• "Default Mail Type" -- set to "Server" to use a file server
• "Server Zone Name" -- set to "" or "*" for the local zone, otherwise, specify a zone name
• "Server Name" -- this is the name that appears in the Chooser
• "Server Volume Name" -- the name of the volume on the server "Server Name"
• "Server Folder Name" -- the name of the folder where bugs will be collected; usually "Bug Reports"
• "Server Default User Name" -- usually "Guest", but can be anything you like. If it's blank, the default user will be the user name specified in the "Personal Info" on the cover card. If "Guest", the user won't be prompted for a user name or password.
G e s t a l t ( U s e I n f o F r o m T h i s M a c . . . )
• On the Configuration Cards, the information for "Use info from this Mac..." is stored in fields made visible by typing "gestaltlist" in the message box. All of the fields you would want to edit are background fields. The list of Macintosh models is there in case the XFCN "MachineName()" fails (I wrote the XFCN for version 1.5).
S e n d i n g P r a c t i c e
• The easy way to unsend a bug is to hold down the option key when clicking on the "Send Report…" button.
C l e a n u p
• If you have added Bugs and Configuration cards and want to clean up the stack for distribution, type "MakePristine" in the message box while on the first card. This will delete unnecessary cards (asking for confirmation for each card), empty the Personal Info (putting back "AppleLink" as the Mail type, and checking Reply Requested), and compact the stack.
M i s c e l l a n e o u s
• These notes are editable. You can add your own notes for personal reference as you like.
• There is an invisible button called "Reset Stack…" on the cover card (visible for the 1994 WWDC)
- type "resetbutton" in message box to toggle it visible/invisible
• Type "personalinfoData" on the cover card to see how the personal info fields are laid out
C h a n g e s S i n c e V e r s i o n 1 . 5
• All Macintoshes are now listed in the Configuration popup (I think)
• OpenDoc and OpenDoc Parts Framework are added to Component popup on the Problem Report card
• The Mail Method on the Personal Info dialog is now radio buttons rather than a text field
• Contains code to allow saving to a file server instead of sending to AppleLink or saving as text
• Can now specify a default Component that's pre-filled in for new bugs (use the ComponentText 'STR ' resource)
• Clicking on the Index now selects the whole line (looks nicer)
• Error checking is slightly smarter on the Personal Info dialog
• CQF Custom code is now integrated for easy modification (see CQF Bug Reporter below)
• Default Configuration Text and problem Report text has been changed
C Q F B u g R e p o r t e r
These are the modifications needed for me to make the Apple Bug Reporter into the CQF Bug Reporter:
• Set the global cqfCustom to TRUE in the openStack handler in the stack script
• Change the Text on the card backgrounds
• Change the About Box
• Add "CQF" to the Help Text
• do 'searchscript "CQF"' to find all script changes that were made for CQF.
C o m i n g I n F u t u r e V e r s i o n s ( m a y b e )
• Import of old bugs from previous versions of the Apple Bug Reporter
• Import of old bugs from bugs saved as text
• "Comments" button to send quick notes back to Apple (CQF version only)
If you have questions specific to this stack, send me e-mail:
